Apparatus and method for recovering a data error in a memory system

ABSTRACT

A memory system includes a memory device and a controller. The memory device includes a plurality of non-volatile memory groups individually storing a plurality of data segments, each data segment corresponding to a codeword. The controller is configured to perform hard decision decoding to correct an error when the error is included in a first data segment among the plurality of data segments, determine whether other data segments associated with the first data segment, among the plurality of data segments, are readable when the hard decision decoding fails, and perform chipkill decoding based on the first data segment and the other data segments when the other data segments are readable.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims the benefit of Korean Patent ApplicationNo. 10-2020-0038757, filed on Mar. 31, 2020, the entire disclosure ofwhich is incorporated herein by reference.

TECHNICAL FIELD

An embodiment of this disclosure relates to a memory system, and moreparticularly, to an apparatus and a method for correcting a data erroroccurring in the memory system.

BACKGROUND

Recently, a paradigm for a computing environment has shifted toubiquitous computing, which enables computer systems to be accessedvirtually anytime and everywhere. As a result, the use of portableelectronic devices, such as mobile phones, digital cameras, notebookcomputers, and the like, are rapidly increasing. Such portableelectronic devices typically use or include a memory system that uses orembeds at least one memory device. The memory system may include a datastorage device. The data storage device can be used as a main storagedevice or an auxiliary storage device of a portable electronic device.

Unlike a hard disk, a data storage device using a non-volatilesemiconductor memory device is advantageous in that it has excellentstability and durability because it has no mechanical driving part(e.g., a mechanical arm), and has high data access speed and low powerconsumption. In the context of a memory system having such advantages,an exemplary data storage device includes a USB (Universal Serial Bus)memory device, a memory card having various interfaces, a solid statedrive (SSD), or the like.

BRIEF DESCRIPTION OF THE DRAWINGS

The description herein makes reference to the accompanying drawingswherein like reference numerals refer to like parts throughout thefigures.

FIG. 1 illustrates a memory system according to an embodiment of thepresent disclosure.

FIG. 2 illustrates a data processing system according to an embodimentof the present disclosure.

FIG. 3 illustrates a memory system according to an embodiment of thepresent disclosure.

FIG. 4 illustrates chipkill decoding performed in a memory system.

FIG. 5 illustrates an error correction operation performed in a memorysystem according to an embodiment of the present disclosure.

FIG. 6 illustrates an error correction operation performed in a memorysystem according to another embodiment of the present disclosure.

FIG. 7 illustrates a method of operating a memory system according to anembodiment of the present disclosure.

FIG. 8 illustrates a method of operating a memory system according toanother embodiment of the present disclosure.

In this disclosure, references to various features (e.g., elements,structures, modules, components, steps, operations, characteristics,etc.) included in “one embodiment,” “example embodiment,” “anembodiment,” “another embodiment,” “some embodiments,” “variousembodiments,” “other embodiments,” “alternative embodiment,” and thelike are intended to mean that any such features are included in one ormore embodiments of the present disclosure, but may or may notnecessarily be combined in the same embodiments.

DETAILED DESCRIPTION

Various embodiments of the present disclosure are described below withreference to the accompanying drawings. Elements and features of thepresent disclosure, however, may be configured or arranged differentlyto form other embodiments, which may be variations of any of thedisclosed embodiments.

In this disclosure, the terms “comprise,” “comprising,” “include,” and“including” are open-ended. As used in the appended claims, these termsspecify the presence of the stated elements and do not preclude thepresence or addition of one or more other elements. The terms in a claimdoes not foreclose the apparatus from including additional components(e.g., an interface unit, circuitry, etc.).

In this disclosure, various units, circuits, or other components may bedescribed or claimed as “configured to” perform a task or tasks. In suchcontexts, “configured to” is used to connote structure by indicatingthat the blocks/units/circuits/components include structure (e.g.,circuitry) that performs one or more tasks during operation. As such,the unit/circuit/component can be said to be configured to perform thetask even when the specified blocks/unit/circuit/component is notcurrently operational (e.g., is not on). Theblocks/units/circuits/components used with the “configured to” languageinclude hardware—for example, circuits, memory storing programinstructions executable to implement the operation, etc. Reciting that ablock/unit/circuit/component is “configured to” perform one or moretasks is expressly intended not to invoke 35 U.S.C. § 112, sixthparagraph, for that block/unit/circuit/component. Additionally,“configured to” can include generic structure (e.g., generic circuitry)that is manipulated by software and/or firmware (e.g., an FPGA or ageneral-purpose processor executing software) to operate in manner thatis capable of performing the task(s) at issue. “Configured to” may alsoinclude adapting a manufacturing process (e.g., a semiconductorfabrication facility) to fabricate devices (e.g., integrated circuits)that are adapted to implement or perform one or more tasks.

As used in the disclosure, the term ‘circuitry’ refers to all of thefollowing: (a) hardware-only circuit implementations (such asimplementations in only analog and/or digital circuitry) and (b)combinations of circuits and software (and/or firmware), such as (asapplicable): (i) to a combination of processor(s) or (ii) to portions ofprocessor(s)/software (including digital signal processor(s)), software,and memory(ies) that work together to cause an apparatus, such as amobile phone or server, to perform various functions) and (c) circuits,such as a microprocessor(s) or a portion of a microprocessor(s), thatrequire software or firmware for operation, even if the software orfirmware is not physically present. This definition of ‘circuitry’applies to all uses of this term in this application, including in anyclaims. As a further example, as used in this application, the term“circuitry” also covers an implementation of merely a processor (ormultiple processors) or portion of a processor and its (or their)accompanying software and/or firmware. The term “circuitry” also covers,for example, and if applicable to a particular claim element, anintegrated circuit for a storage device.

As used herein, these terms “first,” “second,” “third,” and so on areused as labels for nouns that they precede, and do not imply any type ofordering (e.g., spatial, temporal, logical, etc.). The terms “first” and“second” do not necessarily imply that the first value must be writtenbefore the second value. Further, although the terms may be used hereinto identify various elements, these elements are not limited by theseterms. These terms are used to distinguish one element from anotherelement that otherwise have the same or similar names. For example, afirst circuitry may be distinguished from a second circuitry.

Further, the term “based on” is used to describe one or more factorsthat affect a determination. This term does not foreclose additionalfactors that may affect a determination. That is, a determination may besolely based on those factors or based, at least in part, on thosefactors. Consider the phrase “determine A based on B.” While in thiscase, B is a factor that affects the determination of A, such a phrasedoes not foreclose the determination of A from also being based on C. Inother instances, A may be determined based solely on B.

An embodiment of the present disclosure can provide a data processsystem and a method for operating the data processing system, whichincludes components and resources such as a memory system and a host andis capable of dynamically allocating plural data paths used for datacommunication between the components based on usages of the componentsand the resources.

An embodiment of the present disclosure can provide an apparatusconfigured to, when an error is included in data output from anon-volatile memory device in a memory system, read other data stored inneighboring pages in parallel while performing an error recovery orrestoration operation on the data including the error, so as to prepareor perform chipkill decoding to correct a multi-bit error. The memorysystem and an operation method thereof can reduce an increase in latencyduring a data input/output operation due to the error recovery orrestoration operation.

Through this operation performed in the memory system, a plurality ofmeans, algorithms, or methods for recovering an error may be performedin parallel, thereby reducing resource consumption and increasing errorrecovery efficiency rather than a case when all of the means,algorithms, or methods are sequentially performed in a predeterminedorder. Furthermore, an embodiment may provide a method or apparatus ofthe memory system which can improve the error recovery efficiency of thememory system, as well as data input/output performance, operationalreliability, or operational stability of the memory system.

In an embodiment, a memory system can include a memory device includinga plurality of non-volatile memory groups individually storing aplurality of data segments, each data segment corresponding to acodeword; and a controller configured to perform hard decision decodingto correct an error when the error is included in a first data segmentamong the plurality of data segments, determine whether other datasegments associated with the first data segment, among the plurality ofdata segments, are readable when the hard decision decoding fails, andperform chipkill decoding based on the first data segment and the otherdata segments when the other data segments are readable.

The controller can be configured to perform the chipkill decoding andadditional hard decision decoding or soft decision decoding on the firstdata segments in parallel, when the other data segments are readable.

The controller can be configured to skip performing soft decisiondecoding to the first data segments before performing the chipkilldecoding, when the other data segments are readable.

The controller can be configured to perform hard decision decoding onthe other data segments when the other data segments include an error. Amaximum number of hard decision decoding performed on the other datasegments can be less than a number of hard decision decoding performedon the first data segments.

The controller can be configured to perform the hard decision decoding apreset number of times. The hard decision decoding finally fails whenthe error can be not corrected after the hard decision decoding isperformed the preset number of times.

The controller can be configured to determine whether the other datasegments, are readable when a second hard decision decoding to the firstdata segment starts after a first hard decision decoding to the firstdata segment fails.

The controller can be configured to perform read operations for readingthe other data segments in an interleaving manner. The read operationsand the hard decision decoding to the first data segments can beperformed in parallel.

The controller can be configured to stop the chipkill decoding when thehard decision decoding succeeds.

The controller can be configured to store a result of the hard decisiondecoding, and adjust a read voltage based on the result of the harddecision decoding while correcting an error included in the other datasegments.

In another embodiment, a method for operating a memory system, includinga memory device including a plurality of non-volatile memory groupsindividually storing a plurality of data segments, each data segmentcorresponding to a codeword and a controller configured to control thememory device, can include determining whether a first data segmentamong the plurality of data segments includes an error; performing harddecision decoding to correct the error when the error is included in thefirst data segment; determining whether other data segments associatedwith the first data segment, among the plurality of data segments, arereadable when the hard decision decoding fails; and performing chipkilldecoding based on the first data segment and the other data segmentswhen the other data segments are readable.

The method can further include performing the chipkill decoding andadditional hard decision decoding or soft decision decoding to the firstdata segment in parallel, when the other data segments are readable.

The method can further include skipping soft decision decoding to thefirst data segment before performing the chipkill decoding, when theother data segments are readable.

The method can further include performing hard decision decoding to theother data segments when the other data segments include an error. Amaximum number of hard decision decoding performed to the other datasegments can be less than a number of hard decision decoding performedto the first data segment.

The method can further include performing the hard decision decoding apreset number of times. The hard decision decoding finally fails whenthe error can be not corrected after the hard decision decoding isperformed to the first data segment the preset number of times.

The determining whether the other data segments are readable can includedetermining whether the other data segments, are readable when a secondhard decision decoding to the first data segment starts after a firsthard decision decoding to the first data segment fails.

The method can further include performing read operations for readingthe other data segments in an interleaving manner, wherein the readoperations and the hard decision decoding to the first data segment areperformed in parallel.

The method can further include stopping the chipkill decoding when thehard decision decoding succeeds.

The method can further include storing a result of the hard decisiondecoding; and adjusting a read voltage based on the result of the harddecision decoding while recovering an error included in the other datasegments.

In another embodiment, a computer program product tangibly stored on anon-transitory computer readable medium, the computer program productcomprises instructions to cause a multicore processor device thatcomprises a plurality of processor cores with multiple ones of theplurality of processor cores each including a processor and circuitryconfigured to couple the processor to a memory device including aplurality of non-volatile memory groups individually storing a pluralityof data segments to: read a first data segment among the plurality ofdata segments; determine whether the first data segment includes anerror; perform hard decision decoding to correct the error when theerror is included in the first data segment; determine whether otherdata segments associated with the first data segment, among theplurality of data segments, are readable when the hard decision decodingfails; and perform chipkill decoding based on the first data segment andthe other data segments when the other data segments are readable.

The chipkill decoding and additional hard decision decoding or softdecision decoding can be performed to the first data segment inparallel, when the other data segments are readable.

Embodiments of the present disclosure will now be described withreference to the accompanying drawings, wherein like numbers referencelike elements.

FIG. 1 illustrates a memory system 110 according to an embodiment of thepresent disclosure.

Referring to FIG. 1, the memory system 110 may include a memory device150 and a controller 130. The memory device 150 and the controller 130may be physically separated from each other. The memory device 150 andthe controller 130 may be connected via at least one data path. Forexample, the data path may include a channel and/or a way.

According to an embodiment, the memory device 150 and the controller 130may be functionally divided. Further, according to an embodiment, thememory device 150 and the controller 130 may be implemented with asingle chip or a plurality of chips.

The memory device 150 may include a plurality of memory blocks 60. Eachof the plurality of memory blocks 60 may be a group of non-volatilememory cells. Data stored in each of the plurality of memory blocks 60may be removed together by a single erase operation. Although notillustrated, each of the plurality of memory blocks 60 may include aplurality of pages, each of which is a group of non-volatile memorycells, and data may be stored in all memory cells in each page at thesame time during a single program operation or data stored in all memorycells in each page may be output together during a single readoperation.

Although not shown in FIG. 1, the memory device 150 may include aplurality of memory planes or a plurality of memory dies. According toan embodiment, a memory plane may be a logical or a physical partitionincluding at least one memory block 60, a driving circuit capable ofcontrolling an array including a plurality of non-volatile memory cells,and a buffer capable of temporarily storing data inputted to oroutputted from the plurality of non-volatile memory cells.

In addition, according to an embodiment, a memory die may include atleast one memory plane. The memory die may be a set of componentsimplemented on a physically distinguishable substrate. Each memory diemay be connected to the controller 130 through a data path. Each memorydie may include an interface to exchange data and a signal with thecontroller 130.

According to an embodiment, the memory device 150 may include at leastone memory block 60, at least one memory plane, or at least one memorydie. An internal configuration of the memory device 150 may be differentfrom the configuration shown in FIG. 1 according to performance of thememory system 110. That is, embodiments are not limited to theconfiguration shown in FIG. 1.

Referring to FIG. 1, the memory device 150 may include a voltage supplycircuit 70 capable of supplying at least one voltage into the memoryblock 60. The voltage supply circuit 70 may supply a read voltage Vrd, aprogram voltage Vprog, a pass voltage Vpass, or an erase voltage Versinto a non-volatile memory cell included in the memory block 60. Forexample, in a read operation for reading data stored in a selectednon-volatile memory cell included in the memory block 60, the voltagesupply circuit 70 may supply the read voltage Vrd into the selectednon-volatile memory cell. In the program operation for storing data inthe selected non-volatile memory cell included in the memory block 60,the voltage supply circuit 70 may supply the program voltage Vprog intothe selected non-volatile memory cell. Also, during the read operationor the program operation performed on the selected non-volatile memorycell, the voltage supply circuit 70 may supply a pass voltage Vpass intoa non-selected non-volatile memory cell. In the erasing operation forerasing data stored in the memory block 60, the voltage supply circuit70 may supply the erase voltage Vers into the memory block 60.

After programming data in a non-volatile memory cell included in thememory device 150, the controller 130 may read the data. In the dataread by the controller 130, an error (at least 1-bit error) may beoccasionally detected. In an initial usage stage of the memory device150, e.g., when the memory device 150 is a very slightly worn memorydevice, it might be hard to find an error in the read data. However, asthe number of write and erase cycles (P/E cycles) of the memory device150 increases, e.g., as wear of non-volatile memory cells increases, thenumber of errors occurring in the read data may increase. In addition towear of the memory device 150, an error may occur depending on a dataretention time which is a period in which data is safely stored or keepsits value in a non-volatile memory cell in the memory device 150.Typically, the data retention time may be used as a characteristicparameter for operating the memory device 150. An error may occur when avalue of the data stored in the non-volatile memory cell cannot becorrectly recognized due to a characteristic in which a thresholdvoltage of the non-volatile memory cell changes over time.

When the controller 130 performs a read operation, data stored in aplurality of non-volatile memory cells included in the memory device 150are transferred to the controller 130. For example, an input/output(I/O) controller 192 in the controller 130 may perform the readoperation. The input/output controller 192 may transmit a read commandto the memory device 150 through a transceiver 198. The transceiver 198may deliver the read command to the memory device 150 and receive readdata output from the memory device 150. The transceiver 198 may storethe read data, which is transferred from the memory device 150, in amemory 144.

The input/output controller 192 allows decoding/ECC circuitry 196 tocheck and correct an error detected in the read data stored in thememory 144 in response to the read command. For example, thedecoding/ECC circuitry 196 may cure or correct the error included in theread data stored in the memory 144 through an error correction code(ECC). Although the decoding/ECC circuitry 196 has performed an errorcorrection operation using the error correction code (ECC), the error inthe read data stored in the memory 144 may not be corrected. When theerror included in the read data corresponding to the read command is notcorrected, i.e., when the read data is not be recovered, theinput/output controller 192 may determine that the read operationcorresponding to the read command may fail.

As described above, the error included in the read data outputted fromthe memory device 150 may be caused by the change of the thresholdvoltage of the non-volatile memory cell. When the read voltage Vrdsupplied for reading data stored in a plurality of non-volatile memorycells in the memory device 150 is changed in response to a changeddistribution of threshold voltages of the plurality of non-volatilememory cells, an error in of the read data may be reduced. When theerror included in the read data outputted from the memory device 150 isreduced, the decoding/ECC circuitry 196 can easily cure or correct theerror included in the read data.

Regarding the memory system 110, it is desired to increase data storagecapacity while maintaining data accuracy and an input/output speed. Tothis end, the memory system 110 may use an error correction code (ECC)technique and a signal processing technique to efficiently improve datareliability related to the data accuracy. A unit of data to which anerror correction code (ECC) is applied to detect and correct an erroroccurring in data is called a codeword. A codeword has a length of nbits. The n bits includes user data of k bits and parity data of (n−k)bits. A code rate is calculated as (k/n). The higher the code rate, themore user data can be stored in each codeword. Generally, the longer thecodeword and the smaller the code rate, the better the error correctioncapability of the error correction code (ECC).

The decoding/ECC circuitry 196 may decode data or information that isread from the memory device 150 and transmitted through a channel. Thedecoding/ECC circuitry 196 may include a decoder that performs harddecision decoding or soft decision decoding according to how many bitsdata or information is represented as. For example, the decoder mayperform the hard decision decoding using memory cell output informationthat is represented as 1 bit. Herein, the 1-bit information may becalled hard information. Meanwhile, the decoder may perform the softdecision decoding using more accurate memory cell output informationthat is represented as 2 or more bits. The 2- or more bit informationmay be called soft information. The soft decision decoding has astronger error correction capability than the hard decision decoding.But the soft decision decoding may require high complexity in hardwareimplementation and/or high memory consumption, as compared with the harddecision decoding. In addition, generation of the soft information mayrequire longer read latency than generation of the hard information.

An operation of reading data stored in the memory device 150 isperformed through a word line. Data stored in a plurality of memorycells connected to a single word line may be read at the same time. In aread operation, a reference voltage is applied to a word line. Thereference voltage may be compared with a threshold voltage for eachmemory cell to determine data representing information based on acomparison result. For example, the data stored in each memory cell isdetermined whether the threshold voltage has a lower or higher levelthan the reference voltage. Accordingly, one-time sensing (i.e., readingone time) per word line may be required to generate hard information. Ina case of generating 2-bit soft information representing 4 levels, alevel of the reference voltage is changed or adjusted, and three-timesensing (i.e., reading three times) using different levels of thereference voltage may be performed.

When an error is detected in data read from the memory device 150, thememory system 110 may perform an error correction operation step bystep. For example, when an error is found in data read from a singlepage, the decoding/ECC circuitry 196 may perform hard decision decodingon the data. If the error in the corresponding data is not correctedthrough the hard decision decoding, the decoding/ECC circuitry 196 mayalternately perform read bias optimization to adjust a level of the readvoltage Vrd and the soft decision decoding. However, the read biasoptimization and the soft decision decoding may require a relativelylarge number of sensing (reading) operations on memory cells to recoverthe data read from the single page, and thus read latency may beincreased and quality of data (QoS) may be decreased. In an embodimentof the present disclosure, when the hard decision decoding fails atleast one time, the memory system 110 may utilize chipkill decoding torecover and restore the data read from the single page more quickly andefficiently.

Through the chipkill decoding, the memory system 110 may recover orrestore a multi-bit error detected in data read from the memory device150. An error may be generated when data is incorrectly stored in anon-volatile memory cell of the memory device 150 or when data, whichhas been correctly stored in the non-volatile memory cell, may beincorrectly output for various reasons. In an embodiment, the chipkilldecoding may be performed in any of two different ways or in acombination of the two ways. In an embodiment, how to perform thechipkill decoding may be selected or determined according to a hardwareconfiguration of the memory system 110, but might not be changed throughsoftware designed for operations performed by the controller 130.

For applying the chipkill decoding to correct an error, data stored inthe memory device 150 may constitute a codeword. The codeword may be aset of data bits and error check bits which an error correction code(ECC) algorithm provides for error detection and correction. The databits may correspond to user data, and the error check bits maycorrespond to parity data. For example, it is assumed that 256 (=64×4)bits of data associated with each other are stored in four differentlocations within the memory device 150. When a user data area of thememory device 150 is designed in a unit of 64 bits, a size of thecodeword may be 72 bits which includes a 64-bit user data and an 8-biterror correction data (or parity data). In this case, the memory system110 may automatically correct an error when the error is a single-biterror and authentically detect a 2-bit error, which is called SingleError Correction/Double Error Detection (SEC/DED). When errors occur inmultiple-bit data read from the four different locations storing 256(=64×4) bits, the decoding/ECC circuitry 196 may perform the chipkilldecoding to correct the errors included in the 256 (64×4) bits of data.

In an embodiment of the present disclosure, when the hard decisiondecoding performed on each codeword fails, the decoding/ECC circuitry196 may perform the chipkill decoding after sensing/reading codewordsfrom the four different locations in parallel. Accordingly, it ispossible to avoid an increase in read latency and a decrease in qualityof service (QoS) that may be generated by performing soft decisiondecoding after the hard decision decoding.

To improve performance of the chipkill decoding, the memory system 110may include more error correction bits in each codeword to correct morethan one bit error. The number of bits of user data and the number ofbits of error correction data included in each codeword can bedetermined based on various mathematical algorithms that supportcorrection on a multi-bit error. For example, by using a codeword of 144bits consisting of 128 bits of user data and 16 bits of error correctiondata, a 4-bit error within a specific data bit field can be corrected.However, the 4-bit error may be adjacently distributed rather than beingrandomly distributed. Even if two different codewords, e.g., a codewordhaving 128 bits and a codeword having 64 bits, have the same ratio oferror correction bits to user data bits, e.g., 16/128 and 8/64, errorcorrection capability may be improved when a length of a codeword islonger. That is, the longer the codeword, the more bits of error thatcan be corrected or recovered.

In an embodiment, the chipkill decoding may recover or restore an errorthat cannot be corrected using an error correction code (ECC). Thechipkill decoding can be performed on a 4-bit nibble (½ byte). The 4-bitnibble can be called a symbol. If a single nibble is wrong, i.e., whenthe single nibble includes an error, the chipkill decoding can correctall 4 bits in the single nibble as needed. However, if there are errorsin two or more symbols, the chipkill decoding can detect which symbolinclude an error. The controller 130 reads 128-bit user data at a timetogether with 16-bit error check data from the memory device 150supporting the chipkill decoding, and configures 144 bits of data. The128-bit user data can be divided into 324-bit nibbles N0 to N31, and the16-bit error check data can be divided into 44-bit nibbles C0 to C3. Forexample, the controller 130 may use the Galois field.

Based on the Galois multiplication table of 0 to 15 (hexadecimal)described below in Table 1, the four 4-bit check nibbles C0, C1, C2, andC3 generated by dividing the 16-bit error check data can be determinedas shown in the following equations 1 to 4.

TABLE 1 Multiplicand 0 1 2 3 4 5 6 7 8 9 a b c d e f N′ 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 plier 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 2 0 2 4 6 8 ac e 3 1 7 5 b 9 f d 3 0 3 6 5 c f a 9 b 8 d e 7 4 1 2 4 0 4 8 c 3 7 b f6 2 e a 5 1 d 9 5 0 5 a f 7 2 d 8 e b 4 1 9 c 3 6 6 0 6 c a b d 7 1 5 39 f e 8 2 4 7 0 7 e 9 f 8 1 6 d a 3 4 2 5 c b 8 0 8 3 b 6 e 5 d c 4 f 7a 2 9 1 9 0 9 1 8 2 b 3 a 4 d 5 c 6 f 7 e a 0 a 7 d e 4 9 3 f 5 8 2 1 b6 c b 0 b 5 e a 1 f 4 7 c 2 9 d 6 8 9 c 0 c b 7 5 9 e 2 a 6 1 d f 3 4 8d 0 d 9 4 1 c 8 5 2 f b 6 3 e a 7 e 0 e f 1 d 3 2 c 9 7 6 8 4 a b 5 f 0f d 2 9 6 4 b 1 e c 3 8 7 5 aC0=N0+2*N1+3*N2+4*N3+5*N4+6*N5+7*N6+8*N7+9*N8+a*N9+b*N10+c*N11+d*N12+e*N13+f*N14+N15+2*N16+3*N17+4*N18+5*N19+6*N20+7*N21+8*N22+9*N23+a*N24+b*N25+c*N26+d*N27+e*N28+f*N29+N31  [Equation1]C1=N0+N1+N2+N3+N4+N5+N6+N7+N8+N9+N10+N11+N12+N13+N14+N30+N31  [Equation2]C2=N15+N16+N17+N18+N19+N20+N21+N22+N23+N24+N25+N26+N27+N28+N29+N30+N31  [Equation3]C3=N0+9*N1+e*N2+d*N3+b*N4+7*N5+6*N6+f*N7+2*N8+c*N9+5*N10+a*N11+4*N12+3*N13+8*N14+N15+9*N16+e*N17+d*N18+b*N19+7*N20+6*N21+f*N22+2*N23+c*N24+5*N25+a*N26+4*N27+3*N28+8*N29+N30  [Equation4]

In the above-described equations 1 to 4, ‘*’ means the Galoismultiplication, and ‘+’ means an exclusive OR (XOR) operation. Whenreading data, the controller 130 may calculate the four 4-bit checknibbles C0 to C3 generated by dividing the 16-bit error check data, asdescribed above. In addition, the controller 130 may read the data againand repeat the same calculation to generate different four 4-bit checknibbles, i.e., another set C0′ to C3′. Thereafter, the controller 130may generate a nibble set, which is called syndromes of S0, S1, S2, andS3, through Equations 5 to 8 as follows.S0=C0+C0′  [Equation 5]S1=C1+C1′  [Equation 6]S2=C2+C2  [Equation 7]S3=C3+C3′  [Equation 8]

If there are no errors in the data read from the memory device 150, thecheck nibble set C0 to C3 is the same as the check nibble set C0′ toC03′, so that all the syndromes S0 to S3 become ‘0’. However, if thereis an error and thus the check nibble set C0 to C3 is different from thecheck nibble set C0′ to C03′, at least one of the syndromes S0 to S3does not become ‘0’.

For example, it is assumed that there is an error in one of the 324-bitnibbles N0 to N31, e.g., in the 8th nibble N7. Because the 8th nibble N7is included in the equations for calculating the check nibbles C0, C1,and C3, the syndromes S0, S1, and S3 may not be ‘0’. However, thesyndrome S2 becomes ‘0’. First, because the syndrome S1 is not ‘0’ andthe syndrome S2 is ‘0,’ it can be recognized by the controller 130 thatthe error occurred in one of the first 15 nibbles N0 to N14. Whendividing the syndrome S0 by the syndrome S1 and referring to the aboveformula, the divided result becomes 8, so it can be recognized that theerror has occurred in the 8th nibble N7.

Therefore, a current value of the 8th nibble N7 read from the memorydevice 150 is incorrect, and the syndrome S1 can be understood as an XOR(exclusive OR) result of an original correct value and the incorrectvalue of the 8th nibble N7. Therefore, the original correct value can berestored by an XOR operation of the syndrome S1 and the incorrect value.

According to an embodiment, the controller 130 may determine whether anerror is included in data output from a plurality of non-volatile memorycells in the memory device 150 and correct the error when the error isfound. A procedure in which the decoding/ECC circuitry 196 in thecontroller 130 detects an error and corrects the error may be monitoredby a workload detector 194. For example, the workload detector 194 maydetect that the decoding/ECC circuitry 194 performs the read biasoptimization and the soft decision decoding after the hard decisiondecoding fails. When the decoding/ECC circuitry 194 cannot correct anerror included in specific data by performing the hard decision decodingon the specific data, the workload detector 194 may determine whether atleast one another page associated with the specific data, e.g., otherdata transmitted through different channels from other pages located indifferent dies or planes, is readable. When the other data can be readfrom other locations associated with the specific data, the workloaddetector 194 can collect the other data from the other locations tosupport the chipkill decoding independently while the decoding/ECCcircuitry 196 performs the soft decision decoding on the specific data.After the workload detection unit 194 collects the other data, thedecoding/ECC circuitry 196 may perform the chip kill decoding based onthe specific data and the other data. Through this procedure accordingto an embodiment of the present disclosure, when the hard decisiondecoding fails, the controller 130 may perform the chipkill decoding soas to avoid or reduce deterioration of data input and output performancewhich can be caused by performing the read bias optimization and thesoft decision decoding. Such an operation can reduce resources requiredfor the memory system 110 to correct an error.

According to an embodiment, to improve or enhance the error correctionefficiency, the memory system 110 may set or establish detailedoperations with respect to the chipkill decoding. For example, in orderto perform the chipkill decoding in an error correction operationperformed by the decoding/ECC circuitry 196 in the memory system 110,the controller 130 may read other data (additional data) that is locatedat a different location from where the specific data is stored andassociated with the specific data including an error on which the harddecision decoding fails. At this time, the decoding/ECC circuitry 196may perform hard decision decoding on the additional data if an error isfound even in the additional data. Because the additional data has beenread to perform the chipkill decoding, and thus the additional data isnot outputted to an external device, the workload detector 194 may limitthe maximum number of performing the hard decision decoding on theadditional data to 2-3 times that is smaller than the maximum number ofperforming the hard decision decoding on the target data. Performing thehard decision decoding several times on the additional data including anerror before the chipkill decoding is performed may decrease efficiencyof the error correction operation.

According to an embodiment, the decoding/ECC circuitry 196 may store aresult obtained by performing the chipkill decoding on first data in thememory 144 to perform the chipkill decoding on second data, the chipkilldecoding on the second data being performed after the chipkill decodingperformed on the first data. When a lot of errors occur in the firstdata, there is a high possibility that many errors occur in the seconddata stored at locations adjacent to where the first data is located.

Further, after storing an intermediate result obtained during thechipkill decoding in the memory 144, the intermediate result stored inthe memory 144 may be utilized for the hard or soft decision decodingperformed in parallel with the chipkill decoding. In addition, if aresult obtained during the chipkill decoding, e.g., a decoding resultobtained until the hard decision decoding is performed x times, isstored in the memory 144, the controller 130 may apply or utilize thestored result to adjust or optimize the read voltage Vrd for readingother data and correcting an error in the other data.

Hereinafter, referring to FIGS. 2 and 3, some operations performed bythe memory system 110 of FIG. 1 will be described in detail.

FIG. 2 illustrates a data processing system 100 in accordance with anembodiment of the present disclosure. Referring to FIG. 2, the dataprocessing system 100 may include a host 102 engaged or interlocked witha memory system 110.

The host 102 may include, for example, a portable electronic device,such as a mobile phone, an MP3 player, a laptop computer, or the like,or a non-portable electronic device, such as a desktop computer, a gameplayer, a television (TV), a projector, or the like.

The host 102 includes at least one operating system (OS), which cangenerally manage and control functions and operations performed in thehost 102. The OS can provide interoperability between the host 102engaged with the memory system 110 and a user needing and using thememory system 110. The OS may support functions and operationscorresponding to user's requests. By the way of example but notlimitation, the OS may include a general operating system or a mobileoperating system according to mobility of the host 102. The generaloperating system may include a personal operating system or anenterprise operating system according to system requirements or a user'senvironment. The enterprise operating system can be specialized forsecuring and supporting high performance computing. The mobile operatingsystem may be subject to support services or functions for mobility suchas a power saving function.

The host 102 may include a plurality of operating systems. The host 102may execute multiple operating systems interlocked with the memorysystem 110. The host 102 may transmit a plurality of commandscorresponding to user's requests to the memory system 110, therebyperforming operations corresponding to the plurality of commands withinthe memory system 110.

A controller 130 in the memory system 110 may control a memory device150 in response to a request or a command inputted from the host 102.For example, the controller 130 may perform a read operation to providedata read from the memory device 150 to the host 102, and perform awrite operation (or a program operation) to store data inputted from thehost 102 in the memory device 150. In order to perform data input/output(I/O) operations, the controller 130 may control and manage internaloperations for data reading, data programming, data erasing, or thelike.

According to an embodiment, the controller 130 may include a hostinterface (I/F) 132, a processor 134, error correction circuitry (ECC)138, a power management unit (PMU) 140, a memory interface (I/F) 142,and a memory 144. Components included in the controller 130 may varyaccording to an implementation form, an operation performance, or thelike regarding the memory system 110. For example, the memory system 110may be implemented with any of various types of storage devices, whichmay be electrically coupled with the host 102, according to a protocolof a host interface. Non-limiting examples of suitable storage devicesinclude a solid state drive (SSD), a multimedia card (MMC), an embeddedMMC (eMMC), a reduced size MMC (RS-MMC), a micro-MMC, a secure digital(SD) card, a mini-SD card, a micro-SD card, a universal serial bus (USB)storage device, a universal flash storage (UFS) device, a compact flash(CF) card, a smart media (SM) card, a memory stick, and the like.Components may be added to or omitted from the controller 130 based onimplementation of the memory system 110.

The host 102 and the memory system 110 may include a controller or aninterface for transmitting and receiving a signal, data, and the like,under a predetermined protocol. For example, the host interface 132 inthe memory system 110 may include an apparatus capable of transmitting asignal, data, and the like to the host 102 or receiving a signal, data,and the like from the host 102.

The host interface 132 included in the controller 130 may receive asignal, a command (or a request), or data from the host 102. That is,the host 102 and the memory system 110 may use a predetermined protocolto transmit and receive data therebetween. Protocols or interfaces,supported by the host 102 and the memory system 110 for sending andreceiving data therebetween, may include Universal Serial Bus (USB),Multi-Media Card (MMC), Parallel Advanced Technology Attachment (PATA),Small Computer System Interface (SCSI), Enhanced Small Disk Interface(ESDI), Integrated Drive Electronics (IDE), Peripheral ComponentInterconnect Express (PCIE), Serial-attached SCSI (SAS), Serial AdvancedTechnology Attachment (SATA), Mobile Industry Processor Interface(MIPI), and the like. According to an embodiment, the host interface 132is a kind of layer for exchanging data with the host 102 and isimplemented with, or driven by, firmware called a host interface layer(HIL).

The Integrated Drive Electronics (IDE) or Advanced Technology Attachment(ATA), used as one of the interfaces for transmitting and receiving databetween the host 102 and the memory system 110, can use a cableincluding 40 wires connected in parallel to support data transmissionand reception between the host 102 and the memory system 110. When aplurality of memory systems 110 are connected to a single host 102, theplurality of memory systems 110 may be divided into a master and slavesby using a dip switch to which the plurality of memory systems 110 areconnected or based on positions of the plurality of memory systems 110.A memory system 110 set as the master may be used as a main memorydevice. The IDE (ATA) has evolved into Fast-ATA, ATAPI, and Enhanced IDE(EIDE).

The Serial Advanced Technology Attachment (SATA) is a kind of serialdata communication interface that is compatible with various ATAstandards of parallel data communication interface which is used byIntegrated Drive Electronics (IDE) devices. The 40 wires in the IDEinterface can be reduced to six wires in the SATA interface. Forexample, 40 parallel signals for the IDE can be converted into 6 serialsignals for the SATA to implement data transmission and receptionbetween the IDE and the SATA. The SATA has been widely used because ofits faster data transmission and reception rate and its less resourceconsumption in the host 102 used for data transmission and reception.The SATA may support connections of up to 30 external devices to asingle transceiver included in the host 102. In addition, the SATA cansupport hot plugging that allows an external device to be attached to ordetached from the host 102 even while data communication between thehost 102 and another device is executed. Thus, the SATA makes the memorysystem 110 be connected to or disconnected from the host 102 like adevice supported by a universal serial bus (USB) even when the host 102is powered on. For example, in the host 102 having an eSATA port, thememory system 110 may be freely attached to or detached from the host102, like an external hard disk.

The Small Computer System Interface (SCSI) is a kind of serial datacommunication interface used for connection between a computer, aserver, and/or another peripheral device. The SCSI can provide a hightransmission speed, as compared with other interfaces such as the IDEand the SATA. In the SCSI, the host 102 and at least one peripheraldevice (e.g., the memory system 110) are connected in series, but datatransmission and reception between the host 102 and each peripheraldevice may be performed through a parallel data communication. In theSCSI, it is easy to connect or disconnect a device such as the memorysystem 110 to or from the host 102. The SCSI can support connections of15 external devices to a single transceiver included in the host 102.

The Serial Attached SCSI (SAS) can be understood as a serial datacommunication version of the SCSI. In the SAS, not only the host 102 anda plurality of peripheral devices are connected in series, but also datatransmission and reception between the host 102 and each peripheraldevice may be performed in a serial data communication scheme. The SAScan support connection between the host 102 and the peripheral devicethrough a serial cable instead of a parallel cable, so as to easilymanage equipment using the SAS and enhance or improve operationalreliability and communication performance. The SAS may supportconnections of eight external devices to a single transceiver includedin the host 102.

The Non-volatile memory express (NVMe) is a kind of interface based atleast on a Peripheral Component Interconnect Express (PCIe) designed toincrease performance and design flexibility of the host 102, servers,computing devices, and the like equipped with the non-volatile memorysystem 110. Here, the PCIe can use a slot or a specific cable forconnecting the host 102, such as a computing device, and the memorysystem 110, such as a peripheral device. For example, the PCIe can use aplurality of pins (e.g., 18 pins, 32 pins, 49 pins, 82 pins, etc.) andat least one wire (e.g., ×1, ×4, ×8, ×16, etc.), to achieve high speeddata communications over several hundred Mega bits per second (e.g. 250MB/s, 500 MB/s, 985 MB/s, 1969 MB/s, etc.). According to an embodiment,the PCIe scheme may achieve bandwidths of tens to hundreds of Giga bitsper second. The NVMe can support an operation speed of the non-volatilememory system 110, such as an SSD, which operates at a higher speed thana hard disk.

According to an embodiment, the host 102 and the memory system 110 maybe connected to each other through a universal serial bus (USB). The USBis a kind of scalable, hot-pluggable plug-and-play serial interface thatcan provide cost-effective standard connectivity between the host 102and a peripheral device such as a keyboard, a mouse, a joystick, aprinter, a scanner, a storage device, a modem, a video camera, and thelike. A plurality of peripheral devices such as the memory system 110may be coupled to a single transceiver included in the host 102.

Referring to FIG. 2, the error correction circuitry 138 can correcterror bits of data read from the memory device 150, and may include anerror correction code (ECC) encoder and an ECC decoder. Here, the ECCencoder can perform error correction encoding on data that is to beprogrammed in the memory device 150 to thereby generate encoded datainto which parity bits are added, and the encoded data is stored inmemory device 150. The ECC decoder can detect and correct error bitscontained in the data read from the memory device 150 when thecontroller 130 reads the data stored in the memory device 150. In otherwords, after performing error correction decoding on the data read fromthe memory device 150, the error correction circuitry 138 can determinewhether the error correction decoding has succeeded or failed, andoutput an instruction signal (e.g., an error correction success signalor an error correction fail signal). The error correction circuitry 138can use the parity bits, which are generated during the ECC encodingprocess, to correct the error bits of the read data. When the number ofthe error bits is greater than or equal to a threshold number ofcorrectable error bits, the error correction circuitry 138 cannotcorrect the error bits and instead may output an error correction failsignal indicating failure in correcting the error bits. In anembodiment, the error correction circuitry 138 may correspond to thedecoding/ECC circuitry 196 shown in FIG. 1.

According to an embodiment, the error correction circuitry 138 mayperform an error correction operation based on a coded modulation suchas a low density parity check (LDPC) code, a Bose-Chaudhuri-Hocquenghem(BCH) code, a turbo code, a Reed-Solomon (RS) code, a convolution code,a recursive systematic code (RSC), a trellis-coded modulation (TCM), aBlock coded modulation (BCM), and so on. The error correction circuitry138 may include circuits, modules, systems, and/or devices forperforming the error correction operation based on at least one of theabove described codes.

For example, the ECC decoder may perform the hard decision decoding orthe soft decision decoding on data transmitted from the memory device150. Here, the hard decision decoding can be understood as one of twomethods broadly classified for error correction. The hard decisiondecoding may include an operation of correcting an error by readingdigital data of ‘0’ or ‘1’ from a non-volatile memory cell in the memorydevice 150. Because the hard decision decoding is performed using abinary logic signal, a design or a configuration of circuit or algorithmfor performing the hard decision decoding may be simple and a processingspeed of the hard decision decoding may be faster than the soft decisiondecoding.

Meanwhile, the soft decision decoding, which is distinguished from thehard decision decoding, may include an error correction operation basedon threshold voltages of a non-volatile memory cell in the memory device150 that correspond to two or more quantized values, e.g., multi-bitdata, approximate values, an analog value, or the like. The controller130 may receive two or more alphabets or quantized values from aplurality of non-volatile memory cells in the memory device 150, andthen perform a decoding operation on the received values based oninformation generated by characterizing the quantized values as acombination of information such as conditional probability orlikelihood.

The power management unit (PMU) 140 may control electrical powerprovided to the controller 130. The PMU 140 may monitor the electricalpower supplied to the memory system 110, e.g., a voltage supplied to thecontroller 130, and provide the electrical power to components includedin the controller 130. The PMU 140 can not only detect power-on orpower-off, but also generate a trigger signal to enable the memorysystem 110 to back up a current status when the electrical powersupplied to the memory system 110 is unstable. According to anembodiment, the PMU 140 may include a device or a component capable ofaccumulating electrical power that may be used in an emergency.

The memory interface 142 may serve as an interface for handling commandsand data transferred between the controller 130 and the memory device150, to allow the controller 130 to control the memory device 150 inresponse to a command or a request inputted from the host 102. Thememory interface 142 may generate a control signal for the memory device150 and may process data inputted to or outputted from the memory device150 under the control of the processor 134 when the memory device 150 isa flash memory. For example, when the memory device 150 includes a NANDflash memory, the memory interface 142 includes a NAND flash controller(NFC). The memory interface 142 can provide an interface for handlingcommands and data between the controller 130 and the memory device 150.In accordance with an embodiment, the memory interface 142 can beimplemented by executing firmware called a Flash Interface Layer (FIL)as a component for exchanging data with the memory device 150.

According to an embodiment, the memory interface 142 may support an openNAND flash interface (ONFi), a toggle mode or the like for datainput/output with the memory device 150. For example, the ONFi may use adata path (e.g., a channel, a way, etc.) that includes at least onesignal line capable of supporting bi-directional transmission andreception in a unit of 8-bit or 16-bit data. Data communication betweenthe controller 130 and the memory device 150 can be achieved through atleast one interface regarding an asynchronous single data rate (SDR), asynchronous double data rate (DDR), a toggle double data rate (DDR), orthe like.

The memory 144 may act as a working memory of the memory system 110 orthe controller 130 by storing temporary or transactional data occurredor delivered for operations in the memory system 110 and the controller130. For example, the memory 144 may temporarily store read dataoutputted from the memory device 150 in response to a request from thehost 102 before the read data is outputted to the host 102. In addition,the memory 144 may temporarily store write data inputted from the host102 before programming the write data in the memory device 150. When thecontroller 130 controls operations such as a data read operation, a datawrite or program operation, a data erase operation, and so on of thememory device 150, data transmitted or generated between the controller130 and the memory device 150 of the memory system 110 may be stored inthe memory 144. In addition to the read data or the write data, thememory 144 may store information, e.g., map data, read requests, programrequests, etc., necessary for performing operations for inputting oroutputting data between the host 102 and the memory device 150.According to an embodiment, the memory 144 may include one or more of acommand queue, a program memory, a data memory, a write buffer/cache, aread buffer/cache, a data buffer/cache, a map buffer/cache, and so on.

In an embodiment, the memory 144 may be implemented with a volatilememory. For example, the memory 144 may be implemented with a staticrandom access memory (SRAM), a dynamic random access memory (DRAM), orboth. Although FIG. 2 illustrates the memory 144 disposed within thecontroller 130, embodiments are not limited thereto. The memory 144 maybe located within or external to the controller 130. For instance, thememory 144 may be embodied by an external volatile memory having amemory interface transferring data and/or signals between the memory 144and the controller 130.

The processor 134 may control the overall operations of the memorysystem 110. For example, the processor 134 can control a programoperation or a read operation of the memory device 150 in response to awrite request or a read request provided by the host 102. According toan embodiment, the processor 134 may execute firmware to control theprogram operation or the read operation in the memory system 110.Herein, the firmware may be referred to as a flash translation layer(FTL). An example of the FTL will be described in detail referring toFIG. 3. According to an embodiment, the processor 134 may be implementedwith a microprocessor or a central processing unit (CPU).

According to an embodiment, the memory system 110 may be implementedwith at least one multi-core processor. The multi-core processor is akind of circuit or chip in which two or more cores, which are considereddistinct processing regions, are integrated. For example, when aplurality of cores in the multi-core processor drive or execute aplurality of flash translation layers (FTLs) independently, a datainput/output speed (or performance) of the memory system 110 may beimproved. According to an embodiment, the data input/output (I/O)operations in the memory system 110 may be independently performedthrough different cores in the multi-core processor.

The processor 134 in the controller 130 may perform an operationcorresponding to a request or a command inputted from the host 102.Further, the memory system 110 may be independent of a command or arequest inputted from an external device such as the host 102.Typically, an operation performed by the controller 130 in response tothe request or the command inputted from the host 102 may be considereda foreground operation. An operation performed by the controller 130independently regardless of the request or the command inputted from thehost 102 may be considered a background operation. The controller 130can perform the foreground or background operation for reading, writing,or erasing data in the memory device 150. In addition, a parameter setoperation corresponding to a set parameter command or a set featurecommand as a set command transmitted from the host 102 may be considereda foreground operation. Meanwhile, as a background operation performedwithout a command transmitted from the host 102, the controller 130 canperform garbage collection (GC), wear leveling (WL), bad blockmanagement for identifying and processing bad blocks, or the like inrelation to a plurality of memory blocks 152, 154, and 156 included inthe memory device 150.

According an embodiment, substantially similar operations may beperformed as both the foreground operation and the background operation.For example, if the memory system 110 performs garbage collection inresponse to a request or a command inputted from the host 102 (e.g.,Manual GC), the garbage collection can be considered a foregroundoperation. However, when the memory system 110 performs garbagecollection independently of the host 102 (e.g., Auto GC), the garbagecollection can be considered a background operation.

When the memory device 150 includes a plurality of dies (or a pluralityof chips) including non-volatile memory cells, the controller 130 may beconfigured to perform a parallel processing on the memory device 150 inresponse to plural requests or commands inputted from the host 102 inorder to improve performance of the memory system 110. For example, thetransmitted requests or commands may be divided and providedsimultaneously into the plurality of dies or the plurality of chips inthe memory device 150. The memory interface 142 in the controller 130may be connected to the plurality of dies or chips in the memory device150 through at least one channel and at least one way. When thecontroller 130 distributes and stores data in the plurality of diesthrough each channel or each way in response to requests or commandsassociated with a plurality of pages including non-volatile memorycells, plural operations corresponding to the requests or the commandscan be performed simultaneously or in parallel. Such a processing methodor scheme can be considered as an interleaving method. Because a datainput/output speed of the memory system 110 operating with theinterleaving method may be faster than that without the interleavingmethod, data I/O performance of the memory system 110 can be improved.

By the way of example but not limitation, the controller 130 canrecognize statuses regarding a plurality of channels (or ways)associated with the plurality of memory dies included in the memorydevice 150. The controller 130 may determine the status of each channelor each way as one of a busy state, a ready state, an active state, anidle state, a normal state, and an abnormal state. The controller'sdetermination of which channel or way an instruction (and/or data) isdelivered through may be associated with a physical block address. Forexample, which die(s) the instruction (and/or the data) is deliveredinto may be associated with a physical block address. The controller 130may refer to descriptors delivered from the memory device 150. Thedescriptors may be data with a predetermined format or structure andinclude a block or page of parameters describing characteristics of thememory device 150. For instance, the descriptors may include devicedescriptors, configuration descriptors, unit descriptors, and the like.The controller 130 may refer to or use the descriptors to determinewhich channel(s) or way(s) is used to exchange an instruction or data.

Referring to FIG. 2, the memory device 150 in the memory system 110 mayinclude the plurality of memory blocks 152, 154, and 156. Each of theplurality of memory blocks 152, 154, and 156 includes a plurality ofnon-volatile memory cells. According to an embodiment, the memory block152, 154, or 156 may be a group of non-volatile memory cells erasedtogether. The memory block 152, 154, or 156 may include a plurality ofpages, each of which is a group of non-volatile memory cells read orprogrammed together. Although not shown in FIG. 2, each memory block152, 154, or 156 may have a three-dimensional stack structure for a highintegration. Further, the memory device 150 may include a plurality ofdies, each die including a plurality of planes, each plane including theplurality of memory blocks 152, 154, and 156. The memory device 150 maybe differently configured to improve performance of the memory system110.

In the memory device 150 shown in FIG. 2, the plurality of memory blocks152, 154, and 156 are included. The plurality of memory blocks 152, 154,and 156 may be any of different types of memory blocks, such as asingle-level cell (SLC) memory block, a multi-level cell (MLC) memoryblock, or the like, according to the number of bits that can be storedin or represented by one memory cell.

Here, the SLC memory block includes a plurality of pages implemented bymemory cells, each memory cell storing one-bit data. The SLC memoryblock can have high data I/O operation performance and high durability.The MLC memory block includes a plurality of pages implemented by memorycells, each memory cell storing multi-bit data (e.g., two- or more bitsof data). The MLC memory block can have larger storage capacity for thesame space compared to the SLC memory block. The MLC memory block can behighly integrated in a view of storage capacity.

In an embodiment, the memory device 150 may be implemented with MLCmemory blocks such as a double-level cell (DLC) memory block, atriple-level cell (TLC) memory block, a quadruple-level cell (QLC)memory block, and a combination thereof. The double-level cell (DLC)memory block may include a plurality of pages implemented by memorycells, each memory cell capable of storing 2-bit data. The triple-levelcell (TLC) memory block can include a plurality of pages implemented bymemory cells, each memory cell capable of storing 3-bit data. Thequadruple-level cell (QLC) memory block can include a plurality of pagesimplemented by memory cells, each memory cell capable of storing 4-bitdata. In another embodiment, the memory device 150 can be implementedwith a block including a plurality of pages implemented by memory cells,each memory cell capable of storing five or more bits of data.

According to an embodiment, the controller 130 may use a multi-levelcell (MLC) memory block included in the memory device 150 as an SLCmemory block that stores one-bit data in one memory cell. A datainput/output speed of the multi-level cell (MLC) memory block can beslower than that of the SLC memory block. Therefore, when the MLC memoryblock is used as the SLC memory block, a margin for a read or programoperation can be reduced. The controller 130 can utilize a portion ofthe multi-level cell (MLC) memory block as the SLC memory block toachieve a faster data input/output speed. For example, the controller130 may use such a MLC memory block as a buffer to temporarily storedata because the buffer may require a high data input/output speed forimproving performance of the memory system 110.

Further, according to an embodiment, the controller 130 may program datain a multi-level cell (MLC) block a plurality of times withoutperforming an erase operation on the MLC memory block included in thememory device 150. In general, non-volatile memory cells have a featurethat does not support data overwrite. However, the controller 130 mayuse a feature in which a multi-level cell (MLC) may store multi-bit datain order to program plural 1-bit data in the MLC by performing a writeoperation for programming 1-bit data in the MLC a plurality of times.For an MLC overwrite operation, the controller 130 may store the numberof program times as separate operation information when 1-bit data isprogrammed in a non-volatile memory cell. According to an embodiment, anoperation for uniformly levelling threshold voltages of non-volatilememory cells may be carried out before another data is overwritten inthe same non-volatile memory cells.

In an embodiment of the disclosure, the memory device 150 is embodied asa non-volatile memory such as a flash memory, for example, a NAND flashmemory, a NOR flash memory, or the like. Alternatively, the memorydevice 150 may be implemented by at least one of a phase change randomaccess memory (PCRAM), a ferroelectrics random access memory (FRAM), aspin injection magnetic memory (STT-RAM), a spin transfer torquemagnetic random access memory (STT-MRAM), and so on.

Referring to FIG. 3, a controller 130 in a memory system in accordancewith another embodiment of the disclosure is described. The controller130 cooperates with a host 102 and a memory device 150. As illustratedin FIG. 3, the controller 130 includes a host interface 132, a flashtranslation layer (FTL) 240, a memory interface 142, and a memory 144.

Although not shown in FIG. 3, in accordance with an embodiment, the ECCunit 138 illustrated in FIG. 2 may be included in the flash translationlayer (FTL) 240. In another embodiment, the ECC unit 138 may beimplemented as a separate module, circuit, firmware, or the like fromthe flash translation layer (FTL) 240, which is included in orassociated with the controller 130.

The host interface 132 is for handling commands, data, and the liketransmitted from the host 102. By way of example but not limitation, thehost interface 132 may include a command queue 56, a buffer manager 52,and an event queue 54. The command queue 56 may sequentially storecommands, data, and the like received from the host 102 and output themto the buffer manager 52 in an order in which they are stored. Thebuffer manager 52 may classify, manage, or adjust the commands, thedata, and the like, which are received from the command queue 56. Theevent queue 54 may sequentially transmit events for processing thecommands, the data, and the like received from the buffer manager 52.

A plurality of commands or data having the same characteristic, e.g.,read or write commands, may be transmitted from the host 102 to thememory system 110, or commands and data having different characteristicsmay be transmitted to the memory system 110 after being mixed or jumbledby the host 102. For example, a plurality of commands for reading data(read commands) may be delivered to the memory system 110, or a commandfor reading data (read command) and a command for programming/writingdata (write command) may be alternately transmitted to the memory system110. The host interface 132 may sequentially store commands, data, andthe like, which are transmitted from the host 102, to the command queue56. Thereafter, the host interface 132 may estimate or predict what kindof internal operation the controller 130 will perform according to thecharacteristics of commands, data, and the like. The host interface 132may determine a processing order and a priority of commands, data, andthe like based at least on their characteristics. According tocharacteristics of commands, data, and the like transmitted from thehost 102, the buffer manager 52 in the host interface 132 determineswhether the buffer manager 52 should store commands, data, and the likein the memory 144, or whether the buffer manager 52 should deliver thecommands, the data, and the like into the flash translation layer (FTL)240. The event queue 54 receives events, entered from the buffer manager52, which are to be internally executed and processed by the memorysystem 110 or the controller 130 in response to the commands, the data,and the like, and delivers the events to the flash translation layer(FTL) 240 in the order received from the buffer manager 52.

In accordance with an embodiment, the flash translation layer (FTL) 240illustrated in FIG. 3 may work in a multi-thread scheme to perform thedata input/output (I/O) operations. A multi-thread FTL may beimplemented through a multi-core processor using multi-thread includedin the controller 130.

In accordance with an embodiment, the flash translation layer (FTL) 240may include a host request manager (HRM) 46, a map manager (MM) 44, astate manager 42, and a block manager 48. The host request manager (HRM)46 may manage the events entered from the event queue 54. The mapmanager (MM) 44 may handle or control map data. The state manager 42 canperform garbage collection (GC) or wear leveling (WL). The block manager48 may execute commands or instructions onto a block in the memorydevice 150.

By way of example but not limitation, the host request manager (HRM) 46may use the map manager (MM) 44 and the block manager 48 to handle orprocess requests according to read and program commands, and eventswhich are delivered from the host interface 132. The host requestmanager (HRM) 46 may send an inquiry request to the map data manager(MM) 44 to determine a physical address corresponding to the logicaladdress which is entered with the events. The host request manager (HRM)46 may send a read request with the physical address to the memoryinterface 142 to process the read request (to handle the events). On theother hand, the host request manager (HRM) 46 may send a program request(or write request) to the block manager 48 to program data to a specificempty page storing no data in the memory device 150, and then transmit amap update request corresponding to the program request to the mapmanager (MM) 44 to update an item relevant to the programmed data ininformation of mapping logical and physical addresses to each other.

Here, the block manager 48 may convert a program request delivered fromthe host request manager (HRM) 46, the map data manager (MM) 44, and/orthe state manager 42 into a flash program request used for the memorydevice 150 to manage flash blocks in the memory device 150. In order tomaximize or enhance program or write performance of the memory system110 (see FIG. 2), the block manager 48 may collect program requests andsend flash program requests for multiple-plane and one-shot programoperations to the memory interface 142. In an embodiment, the blockmanager 48 sends several flash program requests to the memory interface142 to enhance or maximize parallel processing of the multi-channel andmulti-directional flash controller.

On the other hand, the block manager 48 may manage blocks in the memorydevice 150 according to the number of valid pages, select and eraseblocks having no valid pages when a free block is needed, and select ablock including the least number of valid pages when it is determinedthat garbage collection is necessary. The state manager 42 may performgarbage collection to move valid data to an empty block and erase datastored in blocks containing the moved valid data so that the blockmanager 48 may have enough free blocks that are empty blocks with nodata. If the block manager 48 provides information regarding a block tobe erased to the state manager 42, the state manager 42 may check allflash pages of the block to be erased to determine whether each page ofthe block is valid. For example, to determine validity of each page, thestate manager 42 may identify a logical address recorded in anout-of-band (OOB) area of each page. To determine whether each page isvalid, the state manager 42 may compare the physical address of the pagewith the physical address mapped to the logical address obtained fromthe inquiry request. The state manager 42 sends a program request to theblock manager 48 for each valid page. A mapping table may be updatedthrough the update of the map manager 44 when the program operation iscomplete.

The map manager 44 may manage a logical-physical mapping table. The mapmanager 44 may process requests such as queries, updates, and the like,which are generated by the host request manager (HRM) 46 or the statemanager 42. The map manager 44 may store the entire mapping table in thememory device 150 (e.g., a flash/non-volatile memory) and cache mappingentries according to the storage capacity of the memory 144. When a mapcache miss occurs while processing inquiry or update requests, the mapmanager 44 may send a read request to the memory interface 142 to load arelevant mapping table stored in the memory device 150. When the numberof dirty cache blocks in the map manager 44 exceeds a certain thresholdvalue, a program request may be sent to the block manager 48 so that aclean cache block is made and the dirty map table may be stored in thememory device 150.

On the other hand, when garbage collection is performed, the statemanager 42 copies valid page(s) into a free block, and the host requestmanager (HRM) 46 programs the latest version of data for the samelogical address of the page and currently issues an update request. Whenthe status manager 42 requests the map update in a state in whichcopying of valid page(s) is not completed normally, the map manager 44may not update the mapping table. It is because the map request isissued with old physical information if the status manger 42 requests amap update and a valid page copy is completed later. The map manager 44may perform a map update operation to ensure accuracy only when thelatest map table still points to the old physical address.

FIG. 4 illustrates chipkill decoding performed in a memory system. Thechipkill decoding illustrated in FIG. 4 will be described with referenceto the controller 130 and the memory device 150 shown in FIGS. 1 to 3.

Referring to FIG. 4, the controller 130 in the memory system 110 maystore data based on a configuration of the memory device 150 including aplurality of non-volatile memory cells. The memory device 150 mayinclude a plurality of dies, e.g., Die #1 and Die #2, and each of theplurality of dies Die #1 and Die #2 may include a plurality of planes,e.g., two planes. In FIG. 4, the die Die #1 includes two planes Plane #1and Plane #2, and the die Die #2 includes two planes Plane #3 and Plane#4. Each of the plurality of planes may include a plurality of memoryblocks 60 shown in FIG. 1.

According to an embodiment, the controller 130 and the memory device 150may be connected through a data path including a plurality of channelsand a plurality of ways. The controller 130 and the plurality of diesDie #1 and Die #2 may be connected to a single channel. Each of theplurality of ways connected to a single channel may be connected to acorresponding one of the plurality of dies Die #1 and Die #2. Thecontroller 130 may be connected to each of the plurality of dies Die #1and Die #2 included in the memory device 150 through a data pathincluding at least one channel and at least one way.

In addition, each of the plurality of dies Die #1 and Die #2 may includea plurality of planes. Each plane may include a page-sized buffer orregister. Through this configuration, when data input/output operationsare performed in parallel in the memory device 150 or the datainput/output operations are performed in an interleaving manner, thedata input/output operations may be performed on a plane-by-plane basis.Referring to FIG. 4, four data input/output operations may be performedin parallel on four planes.

Each of data DATA1 and DATA2 stored in the memory device 150 may includea plurality of data segments SEG #1, SEG #2, SEG #3, and SEG #4. Sizesof the data DATA1 and DATA2 may be determined according to aconfiguration of the memory device 150. For example, it is assumed thata size of user data stored in a page included in the memory block 60 is64 bits and a codeword including 8-bit error correction data in additionto the user data is 72(=64+8) bits. Each of the plurality of datasegments SEG #1, SEG #2, SEG #3, and SEG #4 included in each of the dataDATA1 and DATA2 may consist of a single codeword. Accordingly, each ofthe plurality of data segments SEG #1, SEG #2, SEG #3, and SEG #4 mayhave a length of 72 bits. Each of the data DATA1 and DATA2 may include256 (=64×4) bits of user data.

As described in FIG. 1, the data segments SEG #1, SEG #2, SEG #3, andSEG #4, each having 72 bits, may be automatically corrected when asingle-bit error is found in each data segment. When each data segmentincludes a 2-bit error, it may be guaranteed to detect the 2-bit error.

For example, it is assumed that an error has occurred in the first datasegment SEG #1 of the first data DATA1 stored in the first plane Plane#1 of the first die Die #1. The controller 130 may perform hard decisiondecoding on the first data segment SEG #1. When the error occurring inthe first data segment SEG #1 is a single-bit error, the hard decisiondecoding may succeed to correct the error included in the first datasegment SEG #1. However, when the error occurring in the first datasegment SEG #1 is a 2-bit error, the hard decision decoding to correctthe error included in the first data segment SEG #1 may fail. In thiscase, the controller 130 performs the chipkill decoding using the otherdata segments SEG #2, SEG #3, and SEG #4 to correct the 2-bit errorincluded in the first data segment SEG #1 because the other datasegments SEG #2, SEG #3, and SEG #4, are associated with the first datasegment SEG #1.

Referring to FIG. 4, the data segments SEG #1, SEG #2, SEG #3, and SEG#4 of each of the first data DATA1 and the second data DATA2 may bestored in four different planes Plane #1, Plane #2, Plane #3, and Plane#4, respectively.

FIG. 5 illustrates an error correction operation performed in a memorysystem according to an embodiment of the present disclosure.Specifically, FIG. 5 shows the error correction operation that isperformed by the controller 130 shown in FIGS. 1 to 3 when an error isincluded in data output from a specific location (e.g., a target page)of the memory device 150 shown in FIGS. 1 to 3.

Referring to FIG. 5, when the controller 130 detects an error in dataoutput from the target page, a procedure for error correction may beperformed on the data sequentially or serially. The procedure for errorcorrection operation may include a step for performing hard decisiondecoding and another step for performing soft decision decoding. In thestep for the hard decision decoding, a sensing (or reading) operation isperformed to collect hard information used for the hard decisiondecoding. In the step for the soft decision decoding, a sensing (orreading) operation for collecting soft information may be performed. Inthe step for performing the hard decision decoding, the hard decisiondecoding may be performed multiple times. Likewise, the soft decisiondecoding may be performed multiple times in the step for performing thesoft decision decoding.

When the hard decision decoding fails multiple times in the step forperforming the hard decision decoding, the controller 130 may enter thestep for performing the soft decision decoding. When the soft decisiondecoding fails multiple times in the step for performing the softdecision decoding, the controller 130 may perform the chipkill decoding.The chipkill decoding may include a process for correcting an error indata output from a specific plane based on data stored in another plane.The chipkill decoding may correspond to a system to which redundantarrays of independent disks (RAID) are applied.

When the data output from the target page includes a multi-bit error,the controller 130, which sequentially performs the hard decisiondecoding, the soft decision decoding and the chipkill decoding, mayconsume large resources to correct the multi-bit error. Becausegeneration of soft information may require a longer sensing/readingtime, i.e., a longer read latency, than generation of hard information,data input/output performance may be deteriorated when the soft decisiondecoding is performed multiple times after the hard decision decoding isperformed multiple times.

FIG. 6 illustrates an error correction operation performed in a memorysystem according to another embodiment of the disclosure. Specifically,FIG. 6 shows the error correction operation which is performed by thecontroller 130 shown in FIGS. 1 to 3 when an error is included in a datasegment output from a specific location (e.g., a target page) of thememory device 150 shown in FIGS. 1 to 3.

Referring to FIG. 6, when the controller 130 detects that an error isincluded in a data segment output from the target page, a procedure forerror correction may include plural procedures performed in parallel onthe data segment. The procedure for error correction may include a firstprocedure for performing the hard decision decoding, the soft decisiondecoding, and the chipkill decoding in stages, and a second procedurefor performing the chipkill decoding without performing the softdecision decoding.

In the first procedure, when performing the hard decision decoding forerror correction, a sensing (or reading) operation may be performed onthe data segment output from the target page to collect hard informationused for the hard decision decoding. When performing the soft decisiondecoding, a sensing (or reading) operation may be performed to collectsoft information. In the first procedure, the hard decision decoding maybe performed multiple times. Likewise, the soft decision decoding may beperformed multiple times.

According to an embodiment, if the hard decision decoding performed atleast one time on the data segment output from the target page fails inthe first procedure, the controller 130 may start the second procedurefor performing the chipkill decoding. According to an embodiment, thecontroller 130 may perform the first and second procedures in parallel.

In the second procedure, a workload of the controller 130 may bemonitored. Referring to FIGS. 1 and 4, the workload detector 194 maycheck whether another data segment can be sensed or read. Herein, theother data segment may be a data segment associated with the datasegment output from the target page, e.g., a data segment transmittedthrough another channel, a data segment stored in a page included inanother die or another plane, etc.

According to an embodiment, the chipkill decoding included in the secondprocedure may include a plurality of processes for error correction. Forexample, the chipkill decoding may be performed step by step dependingon a complexity or a computational level. If the controller 130 can readanother data segment from another die or another plane, which isassociated with the data segment output from the target page, thecontroller 130 may first perform an operation of low complexity, i.e., alow complexity chipkill decoding, to achieve the chipkill decoding forcorrecting the error included in the data segment output from the targetpage. After performing the low complexity chipkill decoding, thecontroller 130 may store results of the low complexity chipkill decodingin the memory 144 (see FIGS. 1 to 3). Accordingly, the controller 130may perform the chipkill decoding in parallel with the hard decisiondecoding and the soft decision decoding.

According to an embodiment, the controller 130 first performs the harddecision decoding and the soft decision decoding on the target page.After that, when the first procedure for error correction fails, thecontroller 130 performs the chipkill decoding. At this time, thecontroller 130 may utilize stored results of the low complexity chipkilldecoding. Because the low complexity chipkill decoding is performed inadvance while the first procedure for error correction is performed, thecontroller 130 can reduce resources (e.g., time or margin) required forperforming the remaining operations of the chipkill decoding to beperformed after the first procedure for error correction.

According to an embodiment, the controller 130 may detect or monitor aworkload to determine whether it can perform the chipkill decoding whilethe first procedure for error correction is performed.

In addition, according to an embodiment, when it is determined that thecontroller 130 can perform the chipkill decoding, the controller 130 mayperform the chipkill decoding in parallel before performing the softdecision decoding, for example, while the hard decision decoding isperformed after the hard decision decoding has failed at least one time,or perform the chipkill decoding in parallel while the soft decisiondecoding is performed. When the error included in the data segment canbe corrected more quickly through the chipkill decoding performed inparallel, the controller 130 can reduce the input/output performancedegradation of the memory system 110, which is caused by performing thesoft decision decoding multiple times.

While the second procedure for error correction including the lowcomplexity chipkill decoding is performed in parallel with the firstprocedure, the controller 130 may store intermediate informationobtained from the low complexity chipkill decoding in the memory 144.Even when performing the low complexity chipkill decoding using otherdata segments associated with the data segment output from the targetpage, the hard decision decoding on the other data segments may fail iferrors included in some of the other data segments cannot be restoredthrough the low complexity chipkill decoding. In this case, whenintermediate information only for the segments recovered through the lowcomplexity chipkill decoding is stored in the memory 144, the controller130 can recognize in advance the segments whose errors have not beencorrected by the low complexity chipkill decoding. In anotherembodiment, the controller 130 may not store the intermediateinformation obtained from the low complexity chipkill decoding in thememory 144.

As described above, while the hard decision decoding is performedmultiple times and/or the soft decision decoding is performed multipletimes, the controller 130 may perform at least some of the operationsfor the chipkill decoding. For example, the controller 130 may readanother data segment from another location associated with the datasegment read from the target page, and check whether the other datasegment includes an error. In addition, when an error is included in theother data segment output, the controller 130 may perform the harddecision decoding on the other data segment to correct the error. Whenthese processes or operations for the chipkill decoding may be performedin advance by the controller 130, the controller 130 may reduceresources for completing or achieving the chipkill decoding performedbased on plural data segments after the soft decision decoding performedon the data segment read from the target page fails multiple times.

FIG. 7 illustrates a method for operating a memory system according toan embodiment of the disclosure. The method for operating the memorysystem shown in FIG. 7 is for checking whether there is an error in adata segment output from the memory device 150 (refer to FIGS. 1 to 3)and correcting the error. The method for operating the memory system maybe performed by the controller 130 (refer to FIGS. 1 to 4).

Referring to FIG. 7, when an error is included in a subject data segmentoutput from the memory device 150, the memory system 110 capable ofcorrecting the error may perform plural procedures in parallel inresponse to an operation environment. Specifically, the method ofoperating the memory system 110 may include determining whether there isan error in a first data segment output from the memory device 150 (step342). Here, the first data segment may be data corresponding to arequest input from an external device, e.g., the host 102 shown in FIGS.2 and 3. The controller 130 may sense or read a location (e.g., aspecific page) in which the first data segment is stored, and store thefirst data segment in the memory 144. The controller 130 may checkwhether there is an error in the first data segment. Although not shown,when there is no error in the first data segment, the controller 130 maytransmit the first data segment to the external device.

Although not shown, referring to FIG. 4, the first data segment, e.g.,SEG #1, may be associated with other data segments, e.g., SEG #2, SEG#3, and SEG #4, programmed at different locations of the memory device150, e.g., at different planes. Here, association between the first datasegment and the other data segments is caused by a program operation ofthe memory system 110, and the external device (e.g., the host 102) maynot recognize the association. That is, the host 102 may transmit pluraldata segments and a plurality of logical addresses, each of whichcorresponds to each of the plural data segments, to the memory system110. For example, the association between the first data segment and theother data segments may not be related even to interrelationship betweenthe plurality of logical addresses.

When the controller 130 programs the plural data segments to the memorydevice 150, program operations with the plural data segments areperformed in parallel on a plurality of regions (e.g., the planesdescribed in FIG. 4) in the memory device 150. Through the programoperation performed in parallel for the plural data segments, it ispossible for the memory system 110 to improve performance of datainput/output operation. For example, the controller 130 may use an ECCencoder to add an error correction bit to each of plural data segmentsof user data input from the external device to generate a plurality ofcodewords, each codeword including an error correction bit and a datasegment. After generating the plurality of codewords, the controller 130may store each of the plurality of codewords in different locations,e.g., different planes in the memory device 150 (see FIG. 4). Theassociation between the plurality of codewords, i.e., the first datasegment and the other data segments, may occur in these processes. Thatis, the first data segment and the other data segments may correspond tothe plural data segments of the user data and be stored in differentlocations, e.g., different planes in the memory device 150 as shown inFIG. 4.

The method for operating the memory system 110 may include performingthe hard decision decoding to correct an error when the error is foundin the first data segment after the first data segment is read (step344). According to an embodiment, referring to FIGS. 5 to 6, thecontroller 130 may perform the hard decision decoding multiple times onthe first data segment in which the error is found. If the hard decisiondecoding for the first data segment is successful, the memory system 110may stop the error correction operation (step 348). Although notillustrated, when the error is recovered through the hard decisiondecoding, the memory system 110 may output the first data segment whichthe error is corrected to the external device.

The method for operating the memory system 110 may include determiningwhether another data segment associated with the first data segment canbe read when the hard decision decoding fails (step 346). When the harddecision decoding fails at least one time, the controller 130 may detecta workload of the memory system 110. For example, the controller 130 maycheck an operation state of each die or each plane in the memory device150. The controller 130 can monitor a data input/output operationperformed through each die or each plane, and determines whether eachdie or each plane can output a data segment used for error correction(e.g., the chipkill decoding) on the first data segment rather than adata input/output operation corresponding to a request input from theexternal device.

Regardless of whether other data segments associated with the first datasegment can be read, the method for operating the memory system 110 mayinclude performing the soft decision decoding on the first data segmentwhen the hard decision decoding fails (step 350). Here, the softdecision decoding may be performed after the hard decision decodingperformed on the first data segment fails multiple times.

Referring to FIGS. 5 to 6, the controller 130 may perform the softdecision decoding multiple times on the first data segment in which anerror is found. When the soft decision decoding performed on the firstdata segment succeeds, the memory system 110 may stop the errorcorrection (step 348). According to an embodiment, if the soft decisiondecoding on the first data segment fails, the memory system may performthe chipkill decoding based on a plurality of data segments includingthe first data segment and the other data segments associated with thefirst data segment.

Meanwhile, when the other data segments associated with the first datasegment can be read, the method for operating the memory system 110 mayinclude performing the chipkill decoding based on the plurality of datasegments (step 352). The controller 130 may perform all or someoperations for the chipkill decoding in parallel with another errorcorrection procedure such as the hard decision decoding and the softdecision decoding. For example, the controller 130 may perform someoperations for the chipkill decoding in parallel with the hard decisiondecoding or the soft decision decoding, and may hold the remainingoperations for the chipkill decoding until the soft decision decoding onthe first data segment fails. In another example, when the controller130 performs the entire operation for the chipkill decoding, the softdecision decoding on the first data segment may be performed in parallelwith the chipkill decoding, or the soft decision decoding may beskipped.

According to an embodiment, some operations for the chipkill decodingmay be performed after the hard decision decoding fails at least onetime while the hard decision decoding is performed multiple times on thefirst data segment and when the other data segments associated with thefirst data segment are readable. For example, some operations for thechipkill decoding may be performed in parallel while the hard decisiondecoding and/or the soft decision decoding are performed multiple timeon the first data segment.

FIG. 8 illustrates a method for operating a memory system according toanother embodiment of the disclosure. According to an embodiment, themethod for operating the memory system is to check whether there is anerror in a data segment output from the memory device 150 (refer toFIGS. 1 to 3) and correct the error when the error is included in thedata segment. The method for operating the memory system may be executedby the controller 130 (refer to FIGS. 1 to 4).

Referring to FIG. 8, the method for operating the memory system includesreading a first data segment stored in a non-volatile memory device(step 372), checking an error included in the first data segment (step374), reading other data segments associated with the first data segmentwhile performing the hard decision decoding on the first data segment(step 376), and using the other data segments for correcting the errorincluded in the first data segment when the hard decision decoding fails(step 378).

Although not shown, when there is no error in the first data segment, aprocedure for error correction may not be performed. In addition, it canbe understood that the association between the first data segment andthe other data segments is established through an operation forprogramming a plurality of data segments in the memory device 150.

Although not shown, according to an embodiment, when an error occurs inthe first data segment, the hard decision decoding and the soft decisiondecoding may be sequentially performed on the first data segment.Further, when the error included in the first data segment is notcorrected through the hard decision decoding, the controller 130 sensesor reads other data segments associated with the first data segment tocorrect the error included in the first data segment through thechipkill decoding. Through these processes, the controller 130 mayperform error correction operations in parallel.

According to an embodiment, when the hard decision decoding forcorrecting the error in the first data segment fails, the soft decisiondecoding may be performed on the first data segment. In this case, evenif the controller 130 senses or reads the other data segments associatedwith the first data segment, the controller 130 may stand by withoutdirectly utilizing the other data segments to correct the error in thefirst data segment. The controller 130 may check whether an error isalso included in the other data segments. When the error is included inthe other data segments, the error may be corrected through the harddecision decoding. According to an embodiment, when an error is found inthe other data segments, the maximum number of performing the harddecision decoding on the other data segments is less than the number ofperforming the hard decision decoding on the first data segment. This isbecause the controller 130 tries to concentrate and use resources tocorrect the error included in the first data segment rather thancorrecting the error included in the other data segments.

Although not shown, the controller 130 may sequentially or in parallelperform the hard decision decoding, the soft decision decoding, and thechipkill decoding to correct the error included in the first datasegment. When the error included in the first data segment is correctedthrough one of the hard decision decoding, the soft decision decoding,and the chipkill decoding, the error correction operation for the firstdata segment may be terminated.

The memory system according to an embodiment of the present disclosurecan increase efficiency of error recovery.

In addition, the memory system according to another embodiment of thepresent disclosure can reduce resource consumption for error recovery.

Further, the memory system according to another embodiment of thepresent disclosure can improve performance of data input/outputoperations by reducing a delay caused by an error recovery operation.

While the present teachings have been illustrated and described withrespect to the specific embodiments, it will be apparent to thoseskilled in the art in light of the present disclosure that variouschanges and modifications may be made without departing from the spiritand scope of the disclosure as defined in the following claims.

What is claimed is:
 1. A memory system, comprising: a memory deviceincluding a plurality of non-volatile memory groups individually storinga plurality of data segments, each data segment corresponding to acodeword; and a controller configured to perform hard decision decodingto correct an error when the error is included in a first data segmentamong the plurality of data segments, determine whether other datasegments associated with the first data segment, among the plurality ofdata segments, are readable when the hard decision decoding fails, andperform chipkill decoding based on the first data segment and the otherdata segments when the other data segments are readable.
 2. The memorysystem according to claim 1, wherein the controller is configured toperform the chipkill decoding, and additional hard decision decoding orsoft decision decoding on the first data segments in parallel when theother data segments are readable.
 3. The memory system according toclaim 1, wherein the controller is further configured to skip performingsoft decision decoding on the first data segment before performing thechipkill decoding when the other data segments are readable.
 4. Thememory system according to claim 1, wherein the controller is configuredto perform hard decision decoding on the other data segments when theother data segments include an error, wherein a maximum number of harddecision decoding performed on the other data segments is less than anumber of hard decision decoding performed on the first data segment. 5.The memory system according to claim 1, wherein the controller isconfigured to perform the hard decision decoding a preset number oftimes, wherein the hard decision decoding finally fails when the erroris not corrected after the hard decision decoding is performed thepreset number of times.
 6. The memory system according to claim 5,wherein the controller is configured to determine whether the other datasegments are readable when a second hard decision decoding to the firstdata segment starts after a first hard decision decoding to the firstdata segment fails.
 7. The memory system according to claim 6, whereinthe controller is configured to perform read operations for reading theother data segments in an interleaving manner, wherein the readoperations and the hard decision decoding to the first data segment areperformed in parallel.
 8. The memory system according to claim 1,wherein the controller is configured to stop the chipkill decoding whenthe hard decision decoding succeeds.
 9. The memory system according toclaim 1, wherein the controller is configured to store a result of thehard decision decoding, and adjust a read voltage based on the result ofthe hard decision decoding while correcting an error included in theother data segments.
 10. A method for operating a memory system,comprising a memory device including a plurality of non-volatile memorygroups individually storing a plurality of data segments, each datasegment corresponding to a codeword, and a controller configured tocontrol the memory device, the method comprising: determining whether afirst data segment among the plurality of data segments includes anerror; performing hard decision decoding to correct the error when theerror is included in the first data segment; determining whether otherdata segments associated with the first data segment, among theplurality of data segments, are readable when the hard decision decodingfails; and performing chipkill decoding based on the first data segmentand the other data segments when the other data segments are readable.11. The method according to claim 10, further comprising: performing thechipkill decoding, and additional hard decision decoding or softdecision decoding to the first data segment in parallel when the otherdata segments are readable.
 12. The method according to claim 10,further comprising: skipping soft decision decoding to the first datasegment before performing the chipkill decoding when the other datasegments are readable.
 13. The method according to claim 10, furthercomprising: performing hard decision decoding to the other data segmentswhen the other data segments include an error, wherein a maximum numberof hard decision decoding performed to the other data segments is lessthan a number of hard decision decoding performed to the first datasegment.
 14. The method according to claim 10, further comprising:performing the hard decision decoding a preset number of times, whereinthe hard decision decoding finally fails when the error is not correctedafter the hard decision decoding is performed to the first data segmentthe preset number of times.
 15. The method according to claim 14,wherein the determining whether the other data segments are readableincludes: determining whether the other data segments are readable whena second hard decision decoding to the first data segment starts after afirst hard decision decoding to the first data segment fails.
 16. Themethod according to claim 15, further comprising: performing readoperations for reading the other data segments in an interleavingmanner, wherein the read operations and the hard decision decoding tothe first data segment are performed in parallel.
 17. The methodaccording to claim 10, further comprising: stopping the chipkilldecoding when the hard decision decoding succeeds.
 18. The methodaccording to claim 17, further comprising: storing a result of the harddecision decoding; and adjusting a read voltage based on the result ofthe hard decision decoding while recovering an error included in theother data segments.
 19. A computer program product tangibly stored on anon-transitory computer readable medium, the computer program productcomprises instructions to cause a multicore processor device thatcomprises a plurality of processor cores with multiple ones of theplurality of processor cores each comprising a processor and circuitryconfigured to couple the processor to a memory device including aplurality of non-volatile memory groups individually storing a pluralityof data segments to: read a first data segment among the plurality ofdata segments; determine whether the first data segment includes anerror; perform hard decision decoding to correct the error when theerror is included in the first data segment; determine whether otherdata segments associated with the first data segment, among theplurality of data segments, are readable when the hard decision decodingfails; and perform chipkill decoding based on the first data segment andthe other data segments when the other data segments are readable. 20.The computer program product according to claim 19, wherein the chipkilldecoding, and additional hard decision decoding or soft decisiondecoding are performed to the first data segment in parallel when theother data segments are readable.